seed scripts not readable by effective user mysql when mounted volume #429
Conversation
…ipts are not necessarily readable depending on mountpoint perms and after this point in the script all execution is EID mysql
…s a failure mode preventing execution of entrypoint in some version I can't remember
… may not have permission to read a docker volume mounted on the usual initdb.d path
… to assign host address" when service is not available
|
Sorry for the delay! This PR is changing a number of seemingly unrelated things -- can you please describe the problem you're having (and trying to solve here) in more detail? |
|
The failure mode is that seed scripts in /docker-entrypoint-initdb.d are not readable by effective user "mysql". This problem presents when that directory is a Docker volume mount point and the mounted files are not readable by "mysql" user. The proposed solution is to change the entrypoint script to first copy the same seed scripts into the running container, set filemodes to make readable by "mysql" user before dropping privileges with gosu. Unrelated is the problem of sporadic failure during |
|
The failure mode is made clear by #453. As far as copying and chowning the files from |
also
chown -R .../initdb.dto user mysql while root prior togosu exec mysql